-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1:Respect the shim_debug
flag when load tasks
#3276
Conversation
a3910bb
to
a30a190
Compare
Codecov Report
@@ Coverage Diff @@
## master #3276 +/- ##
======================================
Coverage 44.4% 44.4%
======================================
Files 113 113
Lines 12231 12231
======================================
Hits 5431 5431
Misses 5966 5966
Partials 834 834
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think we may want to forward to /dev/null if debug is not set so that we make sure the pipes are flushed and don't backup and block the shim process |
@crosbymichael Great idea! So should we also forward to /dev/null when the shim process starting ? containerd/runtime/v1/shim/client/client.go Lines 70 to 84 in 0485499
|
@darfux ya, lets go ahead and make that change as well |
Currently when we restart containerd it will load all tasks with shim logs whether the `shim_debug` is set or not. Signed-off-by: Li Yuxuan <liyuxuan04@baidu.com>
a30a190
to
66036d9
Compare
Build succeeded.
|
@crosbymichael I found that the stdout&stderr of shim will be set to |
LGTM |
thanks @darfux |
Currently when we restart containerd it will load all tasks with shim
logs whether the
shim_debug
is set or not.Signed-off-by: Li Yuxuan liyuxuan04@baidu.com